Displaying and updating a set of application views

ABSTRACT

The present disclosure generally relates to viewing and updating application views. A device receives a user input, the input, when received initiating display of a plurality of application views of a set of application views. The device, in response to receiving the user input, displays the plurality of application views of the set of application views, wherein the set of application views includes preselected application views and an adaptive view that corresponds to a most recently opened application that is not one of the preselected application views.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application62/348,849, entitled “DISPLAYING AND UPDATING A SET OF APPLICATIONVIEWS”, filed on Jun. 10, 2016, the content of which is herebyincorporated by reference in its entirety.

This application relates to the U.S. patent application Ser. No.15/179,863, entitled “PROVIDING UPDATED APPLICATION DATA FOR PREVIEWINGAPPLICATIONS ON A DISPLAY,” filed on Jun. 10, 2016. This applicationalso relates to the U.S. patent application Ser. No. 15/179,824,entitled “ENHANCED APPLICATION PREVIEW MODE,” filed on Jun. 10, 2016.This application also relates to the U.S. patent application Ser. No.15/179,877, entitled “MEMORY MANAGEMENT FOR APPLICATION LOADING,” filedon Jun. 10, 2016. Each of these applications is hereby incorporated byreference in its entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for managing application views.

BACKGROUND

Many modern electronic devices provide the capability to select and openapplications for accessing the content and functionality of theapplications. Some techniques for selecting and opening applications arebased on scrolling through many applications. These techniques can becumbersome and inefficient.

BRIEF SUMMARY

Some techniques for selecting and opening applications using electronicdevices, however, are generally cumbersome and inefficient. For example,some existing techniques use a complex and time-consuming userinterface, which may include multiple key presses or keystrokes.Existing techniques require more time than necessary, wasting user timeand device energy. This latter consideration is particularly importantin battery-operated devices.

Accordingly, the present disclosure provides electronic devices withfaster, more efficient methods and interfaces for viewing and updatingapplications views for accessing corresponding applications. Suchmethods and interfaces optionally complement or replace other methodsfor selecting and opening applications. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated computing devices, suchmethods and interfaces conserve power and increase the time betweenbattery charges.

In some embodiments, a method, includes, at a device with one or moreprocessors and memory, receiving a user input, the input, when receivedinitiating display of a plurality of application views of a set ofapplication views; and in response to receiving the user input,displaying the plurality of application views of the set of applicationviews, wherein the set of application views includes preselectedapplication views and an adaptive view that corresponds to a mostrecently opened application that is not one of the preselectedapplication views.

In some embodiments, an electronic device, comprising: a display; one ormore processors; one or more input devices; a memory; and one or moreprograms, wherein the one or more programs are stored in memory andconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving a user input, the input,when received initiating display of a plurality of application views ofa set of application views; and in response to receiving the user input,displaying the plurality of application views of the set of applicationviews, wherein the set of application views includes preselectedapplication views and an adaptive view that corresponds to a mostrecently opened application that is not one of the preselectedapplication views.

In some embodiments, a non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a display and one or more input devices, causethe device to: receive a user input, the input, when received initiatingdisplay of a plurality of application views of a set of applicationviews; and in response to receiving the user input, display theplurality of application views of the set of application views, whereinthe set of application views includes preselected application views andan adaptive view that corresponds to a most recently opened applicationthat is not one of the preselected application views.

In some embodiments, a transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a display and one or more input devices, causethe device to: receive a user input, the input, when received initiatingdisplay of a plurality of application views of a set of applicationviews; and in response to receiving the user input, display theplurality of application views of the set of application views, whereinthe set of application views includes preselected application views andan adaptive view that corresponds to a most recently opened applicationthat is not one of the preselected application views.

In some embodiments, a method includes, at a device with one or moreprocessors and memory: receiving a first user input, the first userinput when received, initiating display of a plurality of applicationviews of a set of application views, wherein the set of applicationviews includes preselected application views, the plurality ofapplication views of the set of application views displayed in arespective first state; automatically determining, without user input,whether a predetermined criteria is met for updating at least oneapplication view of the set of application views to a second state; inaccordance with the automatic determination, without user input, thatthe predetermined criteria is met, updating the at least one applicationview of the set of application views to the second state; receiving asecond user input, the second user input, when received, initiatingdisplay of the plurality of application views of the set of applicationviews; and in response to receiving the second user input, displayingthe plurality of application views of the set of application views thatincludes the at least one updated application view updated to the secondstate.

In some embodiments, an electronic device, comprising: a display; one ormore processors; one or more input devices; a memory; and one or moreprograms, wherein the one or more programs are stored in memory andconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving a first user input, thefirst user input when received, initiating display of a plurality ofapplication views of a set of application views, wherein the set ofapplication views includes preselected application views, the pluralityof application views of the set of application views displayed in arespective first state; automatically determining, without user input,whether a predetermined criteria is met for updating at least oneapplication view of the set of application views to a second state; inaccordance with the automatic determination, without user input, thatthe predetermined criteria is met, updating the at least one applicationview of the set of application views to the second state; receiving asecond user input, the second user input, when received, initiatingdisplay of the plurality of application views of the set of applicationviews; and in response to receiving the second user input, displayingthe plurality of application views of the set of application views thatincludes the at least one updated application view updated to the secondstate.

In some embodiments, a non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a display and one or more input devices, causethe device to: receive a first user input, the first user input whenreceived, initiating display of a plurality of application views of aset of application views, wherein the set of application views includespreselected application views, the plurality of application views of theset of application views displayed in a respective first state;automatically determine, without user input, whether a predeterminedcriteria is met for updating at least one application view of the set ofapplication views to a second state; in accordance with the automaticdetermination, without user input, that the predetermined criteria ismet, update the at least one application view of the set of applicationviews to the second state; receive a second user input, the second userinput, when received, initiate display of the plurality of applicationviews of the set of application views; and in response to receiving thesecond user input, display the plurality of application views of the setof application views that includes the at least one updated applicationview updated to the second state.

In some embodiments, a transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a display and one or more input devices, causethe device to: receive a first user input, the first user input whenreceived, initiating display of a plurality of application views of aset of application views, wherein the set of application views includespreselected application views, the plurality of application views of theset of application views displayed in a respective first state;automatically determine, without user input, whether a predeterminedcriteria is met for updating at least one application view of the set ofapplication views to a second state; in accordance with the automaticdetermination, without user input, that the predetermined criteria ismet, update the at least one application view of the set of applicationviews to the second state; receive a second user input, the second userinput, when received, initiate display of the plurality of applicationviews of the set of application views; and in response to receiving thesecond user input, display the plurality of application views of the setof application views that includes the at least one updated applicationview updated to the second state.

In some embodiments, a method, includes at a device with one or moreprocessors and memory: displaying a watch face; receiving a first userinput, the first user input, when received initiating display of aplurality of application views of a set of application views, whereinthe set of application views includes preselected application views; inresponse to receiving the first user input, displaying the plurality ofapplication views of the set of application views; receiving a seconduser input on an application view of the plurality of displayedapplication views, the second user input, when received initiatinglaunch of an application corresponding with the application viewselected by the second user input; and in response to receiving thesecond user input, replacing the plurality of displayed applicationviews by displaying a user interface of the launched application.

In some embodiments, an electronic device, comprising: a display; one ormore processors; one or more input devices; a memory; and one or moreprograms, wherein the one or more programs are stored in memory andconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: displaying a watch face; receivinga first user input, the first user input, when received initiatingdisplay of a plurality of application views of a set of applicationviews, wherein the set of application views includes preselectedapplication views; in response to receiving the first user input,displaying the plurality of application views of the set of applicationviews; receiving a second user input on an application view of theplurality of displayed application views, the second user input, whenreceived initiating launch of an application corresponding with theapplication view selected by the second user input; and in response toreceiving the second user input, replacing the plurality of displayedapplication views by displaying a user interface of the launchedapplication.

In some embodiments, a non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a display and one or more input devices, causethe device to: display a watch face; receive a first user input, thefirst user input, when received initiating display of a plurality ofapplication views of a set of application views, wherein the set ofapplication views includes preselected application views; in response toreceiving the first user input, display the plurality of applicationviews of the set of application views; receive a second user input on anapplication view of the plurality of displayed application views, thesecond user input, when received initiating launch of an applicationcorresponding with the application view selected by the second userinput; and in response to receiving the second user input, replace theplurality of displayed application views by displaying a user interfaceof the launched application.

In some embodiments, a transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device with a display and one or more input devices, causethe device to: display a watch face; receive a first user input, thefirst user input, when received initiating display of a plurality ofapplication views of a set of application views, wherein the set ofapplication views includes preselected application views; in response toreceiving the first user input, display the plurality of applicationviews of the set of application views; receive a second user input on anapplication view of the plurality of displayed application views, thesecond user input, when received initiating launch of an applicationcorresponding with the application view selected by the second userinput; and in response to receiving the second user input, replace theplurality of displayed application views by displaying a user interfaceof the launched application.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for displaying and updating application views, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceother methods for viewing and updating application views.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6N illustrate exemplary user interfaces in accordance with someembodiments.

FIGS. 7A-7L illustrate exemplary user interfaces in accordance with someembodiments.

FIGS. 8A-8C illustrate exemplary user interfaces in accordance with someembodiments.

FIGS. 9A-9I illustrate exemplary user interfaces in accordance with someembodiments.

FIGS. 10A-10Q is a flow diagram illustrating a method for operating anelectronic device in accordance with some embodiments.

FIG. 11 shows an exemplary functional block diagram of an electronicdevice in accordance with some embodiments.

FIGS. 12A-12G illustrate exemplary user interfaces in accordance withsome embodiments.

FIG. 13 is a flow diagram illustrating a method for operating anelectronic device in accordance with some embodiments.

FIG. 14 shows an exemplary functional block diagram of an electronicdevice in accordance with some embodiments.

FIGS. 15A-15C illustrate exemplary user interfaces in accordance withsome embodiments.

FIG. 16 is a flow diagram illustrating a method for operating anelectronic device in accordance with some embodiments.

FIG. 17 shows an exemplary functional block diagram of an electronicdevice in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for displaying and updating application views thatcorrespond to respective applications. For example, some embodiments ofthe interfaces and techniques described below provide an efficient andsimple user interface for selecting an application for launch. Suchtechniques can reduce the cognitive burden on a user who browses throughvarious applications and selecting one of the many applications forlaunch, thereby enhancing productivity. Further, such techniques canreduce processor and battery power otherwise wasted on redundant userinputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-9I illustrate exemplary user interfaces fordisplaying a set of application views. FIGS. 10A-10Q is a flow diagramillustrating methods of displaying a set of application views inaccordance with some embodiments. The user interfaces in FIGS. 6A-9I areused to illustrate the processes described below, including theprocesses in FIGS. 10A-10Q. FIGS. 12A-12G illustrate exemplary userinterfaces for updating a set of application views. FIG. 13 is a flowdiagram illustrating methods of updating a set of application views inaccordance with some embodiments. The user interfaces in FIGS. 12A-12Gare used to illustrate the processes described below, including theprocesses in FIG. 13. FIGS. 15A-15C illustrate exemplary user interfacesfor displaying a set of application views. FIG. 16 is a flow diagramillustrating methods of displaying a set of application views inaccordance with some embodiments. The user interfaces in FIGS. 15A-15Care used to illustrate the processes described below, including theprocesses in FIG. 16.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoW), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 1000,1300 and 1600 (FIGS. 10A-10Q, 13 and 16). A computer-readable storagemedium can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. In some examples,the storage medium is a transitory computer-readable storage medium. Insome examples, the storage medium is a non-transitory computer-readablestorage medium. The non-transitory computer-readable storage medium caninclude, but is not limited to, magnetic, optical, and/or semiconductorstorages. Examples of such storage include magnetic disks, optical discsbased on CD, DVD, or Blu-ray technologies, as well as persistentsolid-state memory such as flash, solid-state drives, and the like.Personal electronic device 500 is not limited to the components andconfiguration of FIG. 5B, but can include other or additional componentsin multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A-1B, 3, and5A-5H). For example, an image (e.g., icon), a button, and text (e.g.,hyperlink) each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and/Di isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, device 500,device 600, or device 900.

FIGS. 6A-9I illustrate exemplary user interfaces for displayingapplication views in a set of application views, in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIGS. 10A-10Q.

FIG. 6A illustrates device 600 with touch sensitive display 602. Device600 may be device 100, 300, or 500 in some embodiments. User interface604 is displayed on touch-sensitive display 602. User interface 604, asillustrated in FIG. 6A, includes watch face 608 of a watch application.

Device 600 includes various input mechanisms that receives user input,such as, rotatable input mechanism 610, that is able to receive arotatable input (and may also receive a push input), and input mechanism612 that is able to receive a push user input.

Referring now to FIGS. 6A-C, in response to receiving user input 614 atinput mechanism 612, a plurality of application views of a set ofapplication views 630 are displayed. The set of application views are asequential list of application views that correspond to respectiveapplications. As shown in FIGS. 6B-6C, in some embodiments, the set ofapplication views 630 include a first application view 631 correspondingto a first application (e.g., friends application), a second applicationview 632 corresponding to second application (e.g., stock application,weather application), a third application view 633 corresponding to athird application, a fourth application view 634 corresponding to afourth application, and a fifth application view 635 corresponding to afifth application. It is noted that, as shown in FIGS. 6A-6C, the set ofapplication views may include one or more application views that are notdisplayed on display 602 at a given time.

In some embodiments, referring to FIGS. 6A-B, in response to user input614, device 600 displays a subset of the set of application views, suchas first application view 631 and second application view 632.Alternatively, in some embodiments, referring to FIGS. 6A and 6C, inresponse to user input 614, device 600 displays a subset of the set ofapplication views, such as application view 633 application view 634,and application view 635.

As shown in FIGS. 6A-C, the application views are a screenshot ofcorresponding applications. Each of the application views in the set ofapplication views 630 are an affordance, that when selected, launch theapplication that corresponds to the application view. For example, theselection (e.g., a touch input on the affordance) of application view631 that corresponds with a friends application launches the friendsapplication. Similarly, the selection of application view 634 thatcorresponds to a music application launches the music application.

In some embodiments, the applications respectively corresponding to theset of application views 630 (e.g., preselected application views andadaptive application view) are stored in memory (e.g., volatile memory).As such, the applications corresponding to the respective applicationviews in the set of application views 630 quickly and easily accessed,(e.g., launch instantaneously), in response to selection of therespective application view.

Device 600, in some embodiments, displays various application viewindicia (or page dots) 640 concurrently with the set of applicationviews. Each application view indicia corresponds to a respectiveapplication view in the set of application views. For example,application view indicia 641 corresponds to application view 631,application view indicia 642 corresponds to application 632 (as shown inFIG. 6B) and application view indicia 643, 644 and 645 respectivelycorrespond to sequential application views 633, 634 and 635 (as shown inFIG. 6C) in the set of application views. As shown in FIGS. 6B-C, thefive separate application view indicia (e.g., application view indicia641, 642, 643, 644 and 645) respectively corresponds to five separateapplication views in the set of application views 630. However, the setof application views 630 can include any number of predefinedapplication views (e.g., ten predefined application views in the set ofapplication views) that correspond to a respective number of applicationview indicia.

The set of application views 630 include preselected application views.The preselected application views are application views corresponding torespective applications, wherein the respective applications have beenpreselected such that their corresponding application views aredisplayed in response to user input 614. As a result, the set ofapplication views 630 provides quick and easy access to the applicationscorresponding to the application views in the set of application views630. In one example, application views 631-634 are preselectedapplication views because they have been affirmatively selected to be inthe set of application views 630. In some embodiments, a user of device600 affirmatively selects the applications (or application views) thatare a part of the set of application views 630, which will be describedin further detail below. In other embodiments, a party (other than theuser) selects one or more applications (or application views), prior toshipping of the device for commercial sale or initial use by the user.

In some embodiments, the preselected application views (and the adaptiveapplication view) remain in the set of application views regardless ofthe operational state of the respective application. The variousoperational states of the application can be a launched (e.g., becomeopened) application, an open or executing application, or a closedapplication. In particular, an open or executing application can be, butis not limited to (1) an active application, which is currentlydisplayed on a display screen of the device that the application isbeing used on, (2) a background application (or background processes),which is not currently displayed, but one or more processes for theapplication are being processed by one or more processors, and (3) asuspended or hibernated application, which is not running, but has stateinformation that is stored in memory (volatile and non-volatile,respectively) and that can be used to resume execution of theapplication.

As a result, in some embodiments, the preselected application views areable to be displayed regardless of the operational state of theapplication. Moreover, in some embodiments, the preselected applicationviews remain in the set of application views until affirmatively removedby the user, which will be described in further detail below.

As seen in FIG. 6D, the set of application views 630 also includes anadaptive application view 635. The adaptive application view correspondsto a most recently opened application that is not currently one of thepreselected application views. The adaptive application view includes ascreenshot of the most recently opened application regardless of theoperational state of the most recently opened application (e.g.,running, suspended, not launched)

Referring to FIG. 6D, application view 635 is an adaptive applicationview that corresponds to a stocks application. In this example, thestocks application is the most recently opened application and thestocks application has not been affirmatively added to the preselectedapplication views (e.g., application views 631-634) of the set ofapplication views 630.

In some embodiments, the stocks application is an open application onthe device and is not a view in the set of application views. While thestock application is open (and displayed in user-interface 604), device600 receives user input 614 is received to display the set ofapplication views. In response to receiving user input 614, device 600displays the adaptive application view that corresponds to the stocksapplication because the stocks application is the most recently openedapplication.

In some embodiments, device 600 displays the adaptive application viewat a terminus (e.g., beginning or end) of the sequence of the set ofapplication views. Alternatively, the adaptive application view is notdisplayed at the terminus of the sequence of application views. In someembodiments, the set of application views includes more than oneadaptive application view that respectively corresponds to the mostrecently opened applications.

In some embodiments, referring to FIG. 6D, while displaying applicationviews 634 and 635 of the set of application views 630, the set ofapplication view indicia 640 are displayed, with each of the applicationview indicia corresponding to a respective application view in the setof application views. In particular, the application view indicia 645that corresponds to the adaptive view 635 is visually distinguished withrespect to the application view indicia corresponding to the preselectedapplication views. In the embodiment depicted in FIG. 6D, applicationview indicia 645 is a hollow indicia (in the highlighted state), whenthe adaptive application view 635 is center focused. In comparison, theapplication view indicia that corresponds to the preselected applicationviews are highlighted as a solid page dote when their respectivepreselected application views are center focused, as seen, for example,in FIG. 6B.

Further as seen in FIG. 6D, the adaptive application view 635 includesaffordance 639 (“add to dock” button) that corresponds to adding theadaptive view to the preselected application views of the set ofapplication views. In response to receiving user input 649 (e.g., tapgesture) for selecting the affordance, the adaptive application view(e.g., application view 635) that corresponds to the most recentlyopened application (e.g., stocks application) is added to thepreselected application views. For example, referring to FIG. 6E, inresponse to user input 649, device 600 adds application view 635 to thepreselected application views of the set of application views such thatapplication view 635 is no longer an adaptive application view. In someembodiments, when an adaptive application view (e.g., stock application)is added to the preselected application views via selection ofaffordance 639, the adaptive application view remains in the set ofapplication view and a new preselected application view (e.g., stockapplication) is created.

In some embodiments, the adaptive application view adapts such that itcorresponds to the most recently opened application that is not one ofthe already existing preselected application views. For example, whenthe stocks application is launched it is the most recently openedapplication. As a result, the adaptive application view corresponds tothe stocks application, as shown in FIG. 6D.

Furthermore, a subsequent new application may be launched (or opened),that is also not associated with the preselected application views. Inresponse to the detecting the launch of the new application, that isalso not associated with the preselected application views, the adaptiveview is updated again to correspond with the new most recently openedapplication. For example, referring to FIG. 6F, when the weatherapplication is the most recently opened application (and not associatedwith the preselected application views) then device 600 updates adaptiveapplication view 635 such that it is corresponds with the weatherapplication (rather than the previous recently opened application suchas the stocks application). In some embodiments, the adaptiveapplication view permits a user to quickly access a recently usedapplication, without having to perform the steps necessary to add theapplication to the set of preselected application views.

In some embodiments, the application view of the most recently openedapplication is center focused upon initiating display of the applicationviews. For example, referring to FIG. 6C, in response to user input atinput mechanism 612, device 600 displays a subset of the set ofapplication views. In particular, device 600 displays a portion ofpreselected application view 633, the full view of preselectedapplication view 634, and a portion of adaptive application view 635.The full view of preselected application view 634 that corresponds tothe music application is fully displayed and centered because the musicapplication that corresponds to preselected application view 634 is themost recently opened application.

Additionally, in some embodiments, the center focused application viewis lit brighter than the one or more adjacent application views. Forexample, application view 634 is lit brighter than sequentially adjacentviews 633 and 635 that are partially displayed. In particular, in someembodiments, the one or more sequentially adjacent views to the centerfocused application view are dimmed with respect to the center focusedapplication view.

In another example, referring to FIG. 6F, in response to user input atinput mechanism 612, a subset of the set of application views aredisplayed. In particular, a portion of preselected application view 634and the full view of adaptive application view 635 are displayed. Thefull view of adaptive application view 635 that corresponds to theweather application is fully displayed and centered because the weatherapplication that corresponds to adaptive application view 635 is themost recently opened application (and is not associated with thepreselected views).

Referring to FIGS. 6F-6G, the weather application associated withadaptive application view 635 can be opened in response to selecting theadaptive application view. For example, while the weather applicationassociated with the adaptive view is not opened, device 600 receivesuser input 650 on the adaptive application view. In response toreceiving user input 650, device 600 launches (or opens) the weatherapplication, as shown in FIG. 6G.

FIGS. 6H-6K illustrates reordering the application views in the set ofapplication views 630. Referring to FIG. 6H (which is similar to FIG.6C, as described above), device 600 receives user input 652 (e.g., hardpress) on preselected application view 634 that corresponds to a musicapplication. User input 652 is for selecting and reordering thepreselected application view in the sequence of application views in theset of application views.

Referring to FIG. 6I, in response to user input 652, device 600 visuallydistinguishes the selected preselected view 634 that corresponds to themusic application from the other views in the set of application views.The visual distinguishing of the selected application view may includechange of size (e.g., larger than the other application views), changeof location (e.g., vertical offset from the other application views),change to being translucent, change to being dimmed, etc. In someembodiments, device 600 reduces each of the displayed application viewsin size in response to user input 652 such that more application viewsare able to be concurrently displayed to aid in reordering of theselected application view.

Textual reference 655, in some embodiments, is displayed associated withthe selected application view. Textual reference 655 indicates thecurrent sequential order of the selected application view (e.g., 4 of 5)in the sequence of the set of application views.

Referring to FIG. 6J, in response detecting movement of user input 652(e.g., slide to the left) to a new location in the sequence of the setof application views, the selected application view 634 translates inaccordance to the detected movement of user input 652 to the newlocation in the sequence of the set of application views. As illustratedin FIG. 6J, device 600 translates the selected application view to a newposition between the application view 631 and application view 632 inthe set of application views 630. As indicated by textual reference 655,in response to the movement of user input 652, the selected applicationview is translated to a new position (e.g., 2 of 5) in the sequence ofthe set of application views.

Referring to FIG. 6K, in response to a break in the contact of userinput 652, device 600 places the selected application view 634 betweenapplication views 631 and 632 such that selected application view 634 isreordered in the sequence of the set of application views. Inparticular, application view 634 is reordered to the second applicationview (from the fourth application view) in the sequence of the set ofapplication views. Additionally, the application views move to makespace for the newly reordered application view. For example, device 600moves application view 631 to the left and/or application views 632 and633 move to right to provide room for the reordering of application view634 to its new position between application view 631 and applicationview 632.

It is contemplated that the techniques for reordering illustrated anddescribed in reference to FIGS. 6H-6K can be applied to reordering otheritems. For example, such techniques may be used to reordercontext-specific user interfaces or watch faces configured for displayon device 600. Exemplary user interfaces and techniques for editingand/or selecting the same are provided in International PatentApplication Serial No. PCT/US2015/034607, titled “Context-Specific UserInterfaces,” filed Jun. 7, 2015, published as WIPO Publication No.WO/2016/022205, which is incorporated by reference herein in itsentirety. In this instance, FIGS. 6H-6K illustrate a mode for reorderinga sequential library of saved user interfaces for display on device 600.The reordering mode of device 600 may be entered, e.g., by a touchgesture on the touch-sensitive display such as a hard press or longpress. 633, 634, and 635 depict preview images representingcontext-specific user interfaces in the library. In some embodiments,preview image 634 represents an active user interface, e.g., the userinterface displayed on device 600 before entering the reordering mode,which is visually distinguished on the display as described above. Inresponse detecting movement of user input 652 (e.g., slide to the left)to a new location in the sequence of the set of user interface previewimages, the selected preview image 634 translates in accordance to thedetected movement of user input 652 to the new location in the sequenceof the set of application views (e.g., as depicted in FIG. 6J). In someembodiments, the stored library of user interfaces is also reorderedaccordingly, e.g., such that the user interface represented by previewimage 634 is reordered at position 2 out of 5 in the library between theuser interfaces represented by preview images 631 and 632. In otherembodiments, rather than depicting the translation of 634 below thesequence of user interface preview images (the rest of which are arrayedin a linear sequence behind and/or above 634), device 600 enlarges thedisplay of preview image 634 larger than 633 and 635 and increases thetransparency of 634, such that the user can perceive preview image 634and the sequence of other preview images behind it on the display. Inresponse detecting movement of user input 652 (e.g., slide to the left)to a new location in the sequence of the set of user interface previewimages, the sequence of preview images translates behind the enlargedand transparent 634 such that it occupies position 2 out of 5 asillustrated in FIG. 6J, then 634 returns to its previous size andtransparency after the user input has ceased.

FIGS. 6L-6N illustrates removing an application view from the set ofapplication views 630. Referring to FIG. 6L, device 600 detects, userinput 653 (e.g., upward swipe gesture) on application view 634 thatcorresponds to a music application. In response to user input 653 thatcorresponds to removing an application view from the set of applicationviews 630, device 600 displays an application view removal userinterface 656 (FIG. 6M). Application view removal user interface 656includes an application view removal affordance 657, and cancelaffordance 658. Application view removal affordance 657, when selectedremoves or deletes the selected application view (e.g., application view634) from the set of application views 630. Cancel affordance 658cancels the process of removing an application view (e.g., applicationview 634) from the set of application views.

Referring to FIG. 6N, in response to selection of application viewremoval affordance 657, device 600 removes the selected application view634 (that is currently in second application view in the set ofapplication views 630) from the set of application views.

Additionally, the application views are moved to close the space left bythe removed application view. For example, device 600 moves applicationview 631 to the right and/or moves application views 632 (and the restof the sequence of the set of application views 630) to the left toclose the open space that once held the removed application view.

As a result of removing an application view, as illustrated in FIGS.6L-6N, the set of application views 630 is reduced to four applicationviews (from five application views). Similarly, the number ofapplication view indicia (or page dots) 640 are reduced to four indicia(from five indicia) that respectively correspond to each of theapplication views in the set of application views.

FIGS. 7A-7D illustrates scrolling through the set of application views.Referring to FIG. 7A, while application view 631 is the focused andcentered application view in the set of application views 630, a swipegesture 710 is received for scrolling through the set of applicationviews 630. In response to receiving swipe gesture 710, device 600scrolls the application views to the adjacent application view 632 (fromapplication view 631) in accordance to the velocity of the swipe gesturebeing below a predetermined velocity, as depicted in FIG. 7B.

Alternatively, in response to receiving swipe gesture 710, theapplication views are scrolled through a plurality of application views(from application view 631), for example, to adaptive application view635, in accordance to the velocity of the swipe gesture being above apredetermined velocity (e.g., 0.1 m/s), as depicted in FIG. 7C. Inparticular, the greater the velocity of the swipe gesture (above thepredetermined velocity), the further the scrolling through applicationview. For example, while application view 631 is the centered andfocused application view, device 600 may scroll to application view 633when the swipe gesture 710 has a first velocity, V₁, that is slightlyabove the predetermined threshold. Similarly, while application view 631is the centered and focused application view, device 600 may scroll toapplication view 634 when the swipe gesture 710 has a second velocity,V₂, that is greater than V₁. Additionally, while application view 631 isthe centered and focused application view, device 600 may scroll toadaptive application view 635 (from application view 631) when the swipegesture 710 has a third velocity, V₃, that is greater than V₂.

Referring now to FIG. 7D, while application view 631 is the focused andcentered application view in the set of application views 630,rotational input 712 for scrolling to an adjacent application view isreceived at rotatable input mechanism 610. In response to receivingrotational input 712 at rotatable input mechanism 610, the applicationviews are scrolled to the adjacent application view 632 (fromapplication view 631), as depicted in FIG. 7B. In some embodiments, thescrolling to the adjacent application view includes a decrease invelocity based on a predetermined coefficient of friction. For example,the speed of the scrolling from application view 631 to application view632 slows down until application view 632 is the new focused andcentered application, wherein the slowing down of the scrolling is basedon a coefficient of friction.

FIGS. 7E-7I illustrate scrolling through the set of application view630. Referring to FIG. 7E, while displaying application views 631 and632 in a display area (e.g., user interface 604), device 600 receivesinput 714 (e.g., press and hold gesture) at an edge 715 of the displayarea (e.g., near bottom edge of user interface 604, or near bottom bezel716 of the touch display screen). Referring to FIG. 7F, in response toreceiving input 714, device 600 moves the displayed application viewsaway from the edge 715 of the display area. In this example, theapplication views translate up and towards the top edge of the displayarea opposite the bottom edge 715. In some embodiments, the applicationviews move away from edge 715 to provide adequate area for a user'sfinger to touch the bottom edge. As a result, a user is able to touch onor around edge 715 without visually blocking the displayed applicationviews.

Referring to FIGS. 7F-7I, movement of the input 714 is detected alongedge 715 (e.g., horizontal scroll gesture to the right). In response tothe detected movement of the input along the bottom edge of the displayarea, the set of application views are scrolled. For example, referringto FIG. 7G, as the input 714 is detected towards the middle of thelength of the edge 715, device 600 displays the application views in themiddle of the sequence of the set of application views (e.g.,application views 632, 634 and 635). Similarly, referring to FIG. 7H, asthe input is detected towards the end of the length of the edge of 715,device 600 displays the application views at the end of the sequence ofthe set of application views (e.g., application views 634 and 635). Insome embodiments, referring to FIG. 7I, in response to a break in input714, devices moves the application views down towards edge 715 intotheir original location (prior to input 714).

In some embodiments, in response to a touch from one terminus of edge715 to the opposite terminus of edge 715, a user can scroll through eachof the application views (regardless of the number of application viewsin the set of application views). Additionally, the initial location ofinput 714 can be anywhere along the length of edge 715. For example, theinitial location of input 714 may be towards the middle of the length ofedge 715, as depicted in FIG. 7G.

FIGS. 7J-7L illustrate dynamic highlighting of application view indicia640. The dynamic highlighting of the application view indicia, asillustrated in FIGS. 7J-7L, corresponds with scrolling from applicationview 631 (that corresponds to application view indicia 641) toapplication view 632 (that corresponds to application view indicia 641),such as described with respect to FIGS. 7A-7B.

Referring to FIG. 7J (and FIG. 7A), while displaying application views631 and 632 of the set of application views 630, a set of applicationview indicia 640 are displayed, wherein each of the application viewindicia (e.g., indicia 641-645) correspond to a respective applicationviews in the set of application views 630. Indicia 641 is highlightedcorresponding to displayed application view 631 that is center focused.In response to receiving user input (e.g., scrolling input) to scroll toadjacent application view 632 (such that application view 632 is centerfocused), application view indicia 642 is highlighted to indicate thatapplication view 632 is the center focused application view. Thehighlighting of application view indicia 642 includes an initialbrightness and a final highlighting brightness, wherein the brightnessof the highlighting increases during the transition from the initialhighlighting brightness to the final highlighting brightness. Forexample, referring to FIG. 7K, indicia 642 includes an initialbrightness, as application view 642 initially transitions into thecenter focused position. Referring to FIG. 7L, indicia 642 includes atransition to a final highlighting brightness that is greater than theinitial highlighting brightness (as shown in FIG. 7K). In someembodiments, the dynamic highlighting acts as if a backlight is movedbetween indicia (e.g., a backlight moves from indicia 641 to 642).

FIGS. 8A-8B illustrates a universal audio application control interface.Referring to FIG. 8A, while an audio application is playing audiocontent (e.g., a third party music application is playing a song),device 600 updates the set of application views 630 with a universalaudio application control interface view 636 that corresponds to auniversal audio application control interface for controlling playbackof the currently playing audio content. The set of application views 630is updated with universal audio application control interface view 636when the set of application views 630 does not correspond to the audioapplication currently playing the audio content. For example, the audioapplication playing the audio content is not a preselected applicationview in the set of application views.

The audio application, that is playing the audio content, includes anapplication-specific control interface to control audio playbackexclusively for the audio application. The universal audio applicationcontrol interface is different and distinct from theapplication-specific control interface. For example, the universal audioapplication control interface is able to control playback of variousthird party music applications (e.g., Pandora, Spotify, SoundCloud) thatare not associated with the preselected application views.

User input 810 on the universal audio application control interface view635 is received. User input 810 is for initiating launching theuniversal audio application control interface.

Referring to FIG. 8B, in response to receiving the user input 810,device 600 launches and displays the universal audio application controlinterface. As a result, the audio content currently playing by the audioapplication is able to be controlled via the universal audio applicationcontrol interface rather than the application-specific controlinterface.

Referring now to FIGS. 8A and 8C, universal audio application controlinterface view 636 includes affordance 639 for adding universal audioapplication control interface view 636 to the preselected applicationviews. In response to user input 812 for adding universal audioapplication control interface view 636 to the preselected applicationviews, device 600 affirmatively adds universal audio application controlinterface view 636 to the preselected application views, as depicted inFIG. 8C.

FIGS. 9A-9I illustrates companion device 900 that is paired to device600. Companion device 900 includes touch sensitive display 902. Userinterface 904 is displayed on touch-sensitive display 902. Companiondevice 900 when paired to device 600 is able to display the applicationviews and perform at least some of the same processes as device 600, asdescribed herein.

Referring to FIGS. 9A-9B, application views can be added to the set ofapplication view 630 via companion device 900 in the same manner asdescribed with respect to device 600, as described herein.

Referring to FIG. 9A, at companion device 900, the adaptive applicationview (e.g., application view 635) includes affordance 639 (e.g., “add todock” button) that corresponds to adding the adaptive view to thepreselected application views of the set of application views. Inresponse to receiving user input 649 (e.g., tap gesture) for selectingthe affordance, the adaptive application view (e.g., application view635) that corresponds to the most recently opened application (e.g.,stocks application) is added to the preselected application views. Forexample, referring to FIG. 9B, in response to user input 649, device 900adds application view 635 to the preselected application views of theset of application views and is no longer an adaptive application view.

Referring to FIGS. 9C-9F, application views can be reordered viacompanion device 900 in the same manner as described with respect todevice 600, as described herein.

FIGS. 9C-9F illustrates reordering the application views in the set ofapplication views 630 via companion device 900 (similar to reorderingdepicted in FIGS. 6H-6K). Referring to FIG. 9C, user input 652 (e.g.,hard press) is received on preselected application view 634 thatcorresponds to a music application. User input 652 is for selecting andreordering the preselected application view in the sequence ofapplication views in the set of application views.

Referring to FIG. 9D, in response to user input 652, device 900 visuallydistinguishes the selected preselected view 634 that corresponds to themusic application from the other views in the set of application views.The visual distinguishing of the selected application view may includechange of size (e.g., larger than the other application views), changeof location (e.g., vertical offset from the other application views),change to being translucent, change to being dimmed, etc. In someembodiments, each of the displayed application views are reduced in sizein response to user input 652 such that more application views are ableto be concurrently displayed to aid in reordering of the selectedapplication view.

Textual reference 655, in some embodiments, is displayed associated withthe selected application view. Textual reference 655 indicates thecurrent sequential order of the selected application view (e.g., 4 of 5)in the sequence of the set of application views.

Referring to FIG. 9E, in response detecting movement of user input 652(e.g., slide to the left) to a new location in the sequence of the setof application views, device 900 translates the selected applicationview 634 in accordance to the detected movement of user input 652 to thenew location in the sequence of the set of application views. Asillustrated in FIG. 9E, the selected application view is translated to anew position between the application view 631 and application view 632in the set of application views 630. As indicated by textual reference655, in response to the movement of user input 652, the selectedapplication view is translated to a new position (e.g., 2 of 5) in thesequence of the set of application views.

Referring to FIG. 9F, in response to a break in the contact of userinput 652, device 900 places the selected application view 634 betweenapplication views 631 and 632 such that selected application view 634 isreordered in the sequence of the set of application views. Inparticular, application view 634 is reordered to the second applicationview (from the fourth application view) in the sequence of the set ofapplication views. Additionally, the application views move to makespace for the newly reordered application view. For example, device 900moves the application view 631 to the left and/or moves applicationviews 632 and 633 to right to provide room for the reordering ofapplication view 634 to its new position between application view 631and application view 632.

FIGS. 9G-9I illustrates removing an application view from the set ofapplication views 630 via companion device 900 (similar to FIGS. 6L-6N).Referring to FIG. 9G, user input 653 (e.g., upward swipe gesture) isdetected on application view 634 that corresponds a music application.User input 653 (e.g., upward swipe gesture) is for removing anapplication view from the set of application views.

Referring to FIG. 9H, in response to user input 653 that corresponds toremoving an application view from the set of application views 630, anapplication view removal user interface 656 is displayed. Applicationview removal user interface 656 includes application view removalaffordance 657 and cancel affordance 658. Application view removalaffordance 657, when selected removes or deletes the selectedapplication view (e.g., application view 634) from the set ofapplication views 630. Cancel affordance 658 cancels the selection of anapplication view (e.g., application view 634) for deletion from the setof application views.

Referring to FIG. 9I, in response to selection of application viewremoval affordance 657, the selected application view 634 (that iscurrently in second application view in the set of application views630) is removed from the set of application views.

Additionally, the application views move to close the space left by theremoved application view. For example, application view 631 moves to theright and/or application views 632 (and the rest of the sequence of theset of application views 630) move to left to close the open space thatonce held the removed application view.

As a result of removing an application view, as illustrated in FIGS.9G-9I, the set of application views 630 is reduced to four applicationviews (from five application views). Similarly, the number ofapplication view indicia (or page dots) 640 are reduced to four indicia(from five indicia) that respectively correspond to each of theapplication views in the set of application views.

FIGS. 10A-10Q is a flow diagram illustrating a method for displayingapplication views in a set of application views using an electronicdevice in accordance with some embodiments. Method 1000 is performed ata device (e.g., 100, 300, 500, 600, or 900) with a display, one orprocessors and memory. Some operations in method 1000 are, optionally,combined, the order of some operations is, optionally, changed, and someoperations are, optionally, omitted.

As described below, method 1000 provides an intuitive way for displayingapplication views in a set of application views. The method reduces thecognitive burden on a user for viewing application views in a set ofapplication views, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user toview application views in a set of application views faster and moreefficiently conserves power and increases the time between batterycharges.

At block 1002, a user input is received at the device (e.g., user input614), the input, when received initiates display of a plurality ofapplication views of a set of application views.

At block 1004, in response to receiving the user input, a plurality ofapplication views of the set of application views (e.g., set ofapplication views 630) are displayed (e.g., FIG. 6B). The set ofapplication views includes preselected application views and an adaptiveview that corresponds to a most recently opened application that is notone of the preselected application views.

In some embodiments, as shown in FIG. 6E, the adaptive view (e.g.,adaptive view 635) that corresponds to a most recently openedapplication is displayed, wherein the adaptive view includes anaffordance (e.g., affordance 639) corresponding to adding the adaptiveview to the preselected application views (1010). A user input (e.g.,input 649) corresponding to selection of the affordance is received(1012). In response to receiving the user input for selecting theaffordance, the adaptive view that corresponds to the most recentlyopened application is added to the preselected application views (1014).

In some embodiments, as shown in FIG. 6D, the set of application viewsare displayed in a sequence, and the adaptive view is displayed at aterminus of the sequence of the set of application views (1006).

In some embodiments, as shown in FIG. 6E, the user input (e.g., userinput 614) is received while displaying an open application that is themost recently opened application that is not one of the preselectedapplication views (1015), and further in response to receiving the userinput, the adaptive view that corresponds to the most recently openedapplication that is not one of the preselected application views isdisplayed (1016). The adaptive view includes an affordance (e.g.,affordance 639) corresponding to adding the adaptive view to thepreselected application views. A user input (e.g., input 649) isreceived corresponding to selection of the affordance (1017). Inresponse to receiving the user input for selecting the affordance, theadaptive view that corresponds to the most recently opened applicationis added to the preselected application views (1018).

In some embodiments, as shown in FIG. 6F, launch of an application isdetected, wherein the adaptive view and the preselected applicationviews of the set of application views do not correspond with thelaunched application (1020). In response to detecting the launch of theapplication, the adaptive view to correspond with the launchedapplication is updated (1021).

In some embodiments, as shown in FIG. 6H, the set of application viewsare displayed in a sequence. In response to receiving user inputcorresponding to display of the sequence of the set of applicationviews, a subset of application views of the sequence of the set ofapplication views are displayed (e.g., application views 633, 634 and635). The displaying the subset of application views comprisesdisplaying an application view of a most recently opened application ina center of the sequence of the subset of application views (1005).

In some embodiments, as shown in FIG. 6H, the set of application viewsare displayed in a sequence. In response to receiving user inputcorresponding to display of the sequence of the set of applicationviews, a subset of application views of the sequence of the set ofapplication views are displayed (e.g., application views 633, 634 and635). The displaying the subset of application views comprisesdisplaying a first application view in the sequence of the set ofapplication in a center of the sequence of the subset of applicationviews (e.g., application view 634), and displaying at least a partialview of a second application view sequential to the first applicationview in the sequence of the set of application views (e.g., applicationview 633 or 634), wherein the second application view is dimmed withrespect to the first application view (1006).

In some embodiments, as shown in FIG. 6G, while the applicationassociated with the adaptive view is not opened, the adaptive view isdisplayed (1022). A user input corresponding to the adaptive view isreceived (1023), and in response to receiving the user inputcorresponding to the adaptive view, the associated application islaunched (1024).

In some embodiments, a portion of the sequence of the set of applicationviews are displayed (1025). As shown in FIG. 6H, an input on anapplication view in a first position in the sequence of the set ofapplication views is received (1026). As shown in FIG. 6I, in responseto the input on the application view, the selected application view withrespect to the other application views in the sequence of the set ofapplication views is visually distinguished (1027). Movement of theinput on the application view to a second position in the sequence ofthe set of application views is detected (1028). As shown in FIG. 6J, inresponse to the detected movement of the input on the application view,the selected application view to the second position in the sequence ofset of application views is moved (1029). As shown in FIG. 6J, a breakof the input on the application view is detected (1030), and in responseto the detected break of the input on the application view, theapplication view is reordered to the second position in the sequence ofset of application views (1031).

In some embodiments, as shown in FIG. 6L, an input on an applicationview of the plurality of application views is received, the input, whenreceived initiates deleting the application view from the set ofapplication views (1032). As shown in FIGS. 6M-6N, in response to theinput on the application view, the application view from the set ofapplication views is deleted (1033).

In some embodiments, as shown in FIG. 7A, a swipe gesture for scrollingthrough the set of application views is received (1034). As shown inFIGS. 7B-7C, in response to receiving the swipe gesture: in accordancewith the velocity of the swipe gesture below a predetermined velocitythreshold, scroll to an adjacent application view, and in accordance tothe velocity of the swipe gesture above the predetermined velocitythreshold, scroll through a plurality of application views of the set ofapplication views (1035).

In some embodiments, as shown in FIG. 7D, a user input is received, theuser input, when received initiates scrolling to an adjacent applicationview in set of application views (1036). A shown in FIG. 7E, in responseto receiving the user input, scrolling to the adjacent application viewin the set of application views, wherein the scrolling to the adjacentapplication view includes a decrease in velocity based on apredetermined coefficient of friction (1037).

In some embodiments, as shown in FIG. 7E, while displaying the pluralityof application views in a display area, an input at a bottom edge of thedisplay area is received, the input, when received initiates scrollingof the application views (1038). As shown in FIG. 7F, in response to theinput at an edge of the display area, move the application views awayfrom the bottom edge of the display area (1039). As shown in FIG. 7G,movement of the input along the bottom edge of the display area isdetected (1040). As shown in FIGS. 7G-7H, in response to the detectedmovement of the input along the bottom edge of the display area, scrollthrough the set of application views (1041).

In some embodiments, as shown in FIG. 6F, while displaying the pluralityof application views of the set of application views, a set ofapplication view indicia is displayed (e.g., indicia 640). Each of theapplication view indicia corresponds to a respective application view inthe set of application views. The application view indicia correspondingto the adaptive view is visually distinguished with respect to theapplication view indicia corresponding to the preselected applicationviews (1042).

In some embodiments, as shown in FIG. 7J, while displaying the pluralityof application views of the set of application views, a set ofapplication view indicia is displayed, wherein each of the applicationview indicia corresponds to a respective application view in the set ofapplication views (1043). As shown in FIG. 7J, an indicia correspondingto a displayed application view is highlighted 1044). A user input isreceived, the user input, when received for scrolling to anotherapplication view in the set of application views (1045). In response toreceiving the user input, scroll to the another application view (1046).As shown in FIGS. 7K-7L, in accordance to scrolling to the anotherapplication view, highlight an application view indicia corresponding tothe another application view, wherein the highlighting the applicationview corresponding to the another application view includes an initialhighlighting brightness, and a final highlighting brightness, whereinthe brightness of the highlighting increases during the transition fromthe initial highlighting brightness to the final highlighting brightness(1047).

In some embodiments, while an audio application is playing audiocontent, wherein the audio application includes an application-specificcontrol interface and the set of application views does not include anapplication view corresponding to the audio application (1046): as shownin FIG. 8A, the set of application views is updated with a universalaudio application control interface view corresponding to a universalaudio application control interface, wherein the universal audioapplication control interface is different than the application-specificcontrol interface that is not a part of the dock (1047). A user input onthe universal audio application control interface view is received(e.g., input 810), the user input, when received initiating launchingthe universal audio application control interface (1048). As shown inFIG. 8B, in response to receiving the user input, the universal audioapplication control interface for controlling the playback of the audiocontent playing on the audio application is displayed (1049).

In some embodiments, as shown in FIG. 8A, wherein the universal audioapplication control interface view includes an affordance correspondingto adding the universal audio application control interface view to theset of application views (1050). As shown in FIG. 8C, a user input forselecting the affordance is received (1051), and in response toreceiving the user input for selecting the affordance, add the universalaudio application control interface view to the set of application views(1052).

In some embodiments, as shown in FIG. 9A, at a companion device (e.g.,device 900) with one or more processors and memory that is paired withthe device (e.g., device 600) the adaptive view that corresponds to amost recently opened application is displayed, wherein the adaptive viewincludes an affordance corresponding to adding the adaptive view to thepreselected application views (1053). As shown in FIG. 9B, a user inputfor selecting the affordance is received (1054), and in response toreceiving the user input for selecting the affordance, the adaptive viewthat corresponds to the most recently opened application is added to thepreselected application views (1055).

In some embodiments, as shown in FIG. 9C. at a companion device (e.g.,device 900) with one or more processors, touchscreen and memory that ispaired with the device (e.g., device 600) a portion of the sequence ofthe set of application views is displayed (1056). An input is receivedat a location on the touchscreen displaying an application view in afirst position in the sequence of the set of application views (1057).As shown in FIG. 9D, in response to the input, the selected applicationview is visually distinguished with respect to the other applicationviews in the sequence of the set of application views (1058). Movementis detected, without breaking contact with touchscreen, of the input onthe application view to a second position in the sequence of the set ofapplication views (1059). As shown in FIG. 9E, in response to thedetected movement of the input on the application view, the selectedapplication view is moved to the second position in the sequence of setof application views (1060). As shown in FIG. 9F, a break of the inputwith the touchscreen is detected (1061), and in response to the detectedbreak of the input with the touchscreen, the application view isreordered to the second position in the sequence of set of applicationviews (1062).

In some embodiments, as shown in FIG. 9G, at a companion device (e.g.,device 900) to the device (e.g., device 600), wherein the companiondevice includes one or more processors and memory that is paired withthe device, an input is received on an application view of the pluralityof application views, the input, when received initiates deletion of theapplication view from the set of application views (1063). As shown inFIG. 9I, in response to the input on the application view, theapplication view is deleted from the set of application views (1064).

Note that details of the processes described above with respect tomethod 1000 (e.g., FIGS. 10A-10Q) are also applicable in an analogousmanner to the methods described below. For example, method 1300optionally includes one or more of the characteristics of the variousmethods described above with reference to method 1000. For example,method 1300 includes updating application views that can be optionallyimplemented in method 1000. For brevity, these details are not repeatedbelow.

In accordance with some embodiments, FIG. 11 shows an exemplaryfunctional block diagram of an electronic device 1100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 1100 are configured to perform the techniques described above.The functional blocks of the device 1100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 11 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 11, an electronic device 1100 includes a display unit1102 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 1104 configured to receive contacts, and aprocessing unit 1106 coupled to the display unit 1102 and, optionally,the touch-sensitive surface unit 1104. In some embodiments, theprocessing unit 1106 includes a receiving unit 1110, an adding unit1112, an updating unit 1114, a reordering unit 1116, a deleting unit1118, a scrolling unit 1120, a highlighting unit 1122, detecting unit1124, launching unit 1126, visually distinguishing unit 1128, and movingunit 1130.

The processing unit 1106 is configured to: receive a user input at thedevice (e.g., with the receiving unit 1110), the input, when receivedinitiates display of a plurality of application views of a set ofapplication views. In response to receiving the user input, displaying(e.g., with display unit 1102) the plurality of application views of theset of application views 630. The set of application views includespreselected application views and an adaptive view that corresponds to amost recently opened application that is not one of the preselectedapplication views.

In some embodiments, the processing unit 1106 is configured to: display(e.g., with the display unit 1102) the adaptive view that corresponds toa most recently opened application, wherein the adaptive view includesan affordance corresponding to adding the adaptive view to thepreselected application views. Receive a user input corresponding toselection of the affordance. In response to receiving the user input forselecting the affordance, add (e.g., with the adding unit 1112) theadaptive view that corresponds to the most recently opened applicationto the preselected application views

In some embodiments, the processing unit 1106 is configured to: display(e.g., with the display unit 1102) the set of application views in asequence, and display (e.g., with the display unit 1102) the adaptiveview at a terminus of the sequence of the set of application views.

In some embodiments, the processing unit 1106 is configured to: receive(e.g., with the receiving unit 1110) the user input while displaying anopen application that is the most recently opened application that isnot one of the preselected application views, and further in response toreceiving the user input, the adaptive view that corresponds to the mostrecently opened application that is not one of the preselectedapplication views is displayed. The adaptive view includes an affordancecorresponding to adding the adaptive view to the preselected applicationviews. Receive (e.g., with receiving unit 1110) user input correspondingto selection of the affordance. In response to receiving the user inputfor selecting the affordance, add (e.g., with the adding unit 1112) theadaptive view that corresponds to the most recently opened applicationis added to the preselected application views.

In some embodiments, the processing unit 1106 is configured to: detectlaunch (e.g., with the detecting unit 1124) of an application, whereinthe adaptive view and the preselected application views of the set ofapplication views do not correspond with the launched application. Inresponse to detecting the launch of the application, update (e.g., withthe updating unit 1114) the adaptive view to correspond with thelaunched application.

In some embodiments, the processing unit 1106 is configured to: display(e.g., with the displaying unit 1102) the set of application views in asequence. In response to receiving user input corresponding to displayof the sequence of the set of application views, display (e.g., with thedisplaying unit 1102) a subset of application views of the sequence ofthe set of application views. The processing unit 1106 is furtherconfigured to: display (e.g., with the displaying unit 1102) anapplication view of a most recently opened application in a center ofthe sequence of the subset of application views.

In some embodiments, the processing unit 1106 is configured to: display(e.g., with the displaying unit 1102) the set of application views in asequence. In response to receiving user input corresponding to displayof the sequence of the set of application views, display (e.g., with thedisplaying unit 1102) a subset of application views of the sequence ofthe set of application views. The displaying the subset of applicationviews comprises displaying a first application view in the sequence ofthe set of application in a center of the sequence of the subset ofapplication views, and displaying at least a partial view of a secondapplication view sequential to the first application view in thesequence of the set of application views, wherein the second applicationview is dimmed with respect to the first application view.

In some embodiments, the processing unit 1106 is configured to: whilethe application associated with the adaptive view is not opened, display(e.g., with the displaying unit 1102) the adaptive view. Receive (e.g.,with receiving unit 1110) user input corresponding to the adaptive view,and in response to receiving the user input corresponding to theadaptive view, launch the associated application (e.g., with launchingunit 1126).

In some embodiments, the processing unit 1106 is configured to: display(e.g., with display unit 1102) a portion of the sequence of the set ofapplication views. Receive an input (e.g., with receiving unit 1110) onan application view in a first position in the sequence of the set ofapplication views. In response to the input on the application view,visually distinguish (e.g., with visually distinguishing unit 1128) theselected application view with respect to the other application views inthe sequence of the set of application views. Detecting movement (e.g.,with detecting unit 1124) of the input on the application view to asecond position in the sequence of the set of application views. Inresponse to the detected movement of the input on the application view,move (e.g., with moving unit 1130) the selected application view to thesecond position in the sequence of set of application views. Detect abreak of the input on the application view (e.g., with detecting unit1124), and in response to the detected break of the input on theapplication view, reorder (e.g., with reordering unit 1116) theapplication view to the second position in the sequence of set ofapplication views is reordered.

In some embodiments, the processing unit 1106 is configured to: receive(e.g., with receiving unit 1110) an input on an application view of theplurality of application views, the input, when received initiatesdeletion (e.g., with deleting unit 1118) the application view from theset of application views. In response to the input on the applicationview, delete (e.g., with deleting unit 1118) the application view fromthe set of application views.

In some embodiments, the processing unit 1106 is configured to: receive(e.g., with receiving unit 1110) a swipe gesture for scrolling throughthe set of application views. In response to receiving the swipegesture: in accordance with the velocity of the swipe gesture below apredetermined velocity threshold, scroll (e.g., with scrolling unit1120) to an adjacent application view, and in accordance to the velocityof the swipe gesture above the predetermined velocity threshold, scroll(e.g., with scrolling unit 1120) through a plurality of applicationviews of the set of application views.

In some embodiments, the processing unit 1106 is configured to: receive(e.g., with receiving unit 1110) a user input, the user input, whenreceived initiating scrolling to an adjacent application view in set ofapplication views. In response to receiving the user input, scroll(e.g., with scrolling unit 1120) to the adjacent application view in theset of application views, wherein the scrolling to the adjacentapplication view includes a decrease in velocity based on apredetermined coefficient of friction.

In some embodiments, the processing unit 1106 is configured to: whiledisplaying the plurality of application views in a display area, receive(e.g., with receiving unit 1110) an input at a bottom edge of thedisplay area, the input, when received initiates scrolling of theapplication views. In response to the input at an edge of the displayarea, move (e.g., with moving unit 1130) the application views away fromthe bottom edge of the display area. Movement of the input along thebottom edge of the display area is detected. In response to the detectedmovement of the input along the bottom edge of the display area, scroll(e.g., with scrolling unit 1120) through the set of application views.

In some embodiments, the processing unit 1106 is configured to: whiledisplaying the plurality of application views of the set of applicationviews, display (e.g., with display unit 1102 a set of application viewindicia is displayed. Each of the application view indicia correspondsto a respective application view in the set of application views. Theapplication view indicia corresponds to the adaptive view is visuallydistinguished with respect to the application view indicia correspondingto the preselected application views.

In some embodiments, the processing unit 1106 is configured to: whiledisplaying the plurality of application views of the set of applicationviews, display (e.g., with display unit 1102) a set of application viewindicia, wherein each of the application view indicia corresponds to arespective application view in the set of application views. Highlight(e.g., with highlighting unit 1122) an indicia corresponding to adisplayed application view. Receive (e.g., with receiving unit 1110) auser input, the user input, when received for scrolling to anotherapplication view in the set of application views. In response toreceiving the user input, scroll (e.g., with scrolling unit 1120) to theanother application view. In accordance to scrolling to the anotherapplication view, highlight (e.g., with highlighting unit 1122) anapplication view indicia corresponding to the another application view,wherein the highlighting the application view corresponding to theanother application view includes an initial highlighting brightness,and a final highlighting brightness, wherein the brightness of thehighlighting increases during the transition from the initialhighlighting brightness to the final highlighting brightness.

In some embodiments, the processing unit 1106 is configured to: while anaudio application is playing audio content, wherein the audioapplication includes an application-specific control interface and theset of application views does not include an application viewcorresponding to the audio application, update (e.g., with the updatingunit 1114) the set of application views with a universal audioapplication control interface view corresponding to a universal audioapplication control interface, wherein the universal audio applicationcontrol interface is different than the application-specific controlinterface that is not a part of the dock. Receive (e.g., with receivingunit 1110) user input on the universal audio application controlinterface view, the user input, when received initiating launching theuniversal audio application control interface. In response to receivingthe user input, display (e.g., with the display unit 1102) the universalaudio application control interface for controlling the playback of theaudio content playing on the audio application.

In some embodiments, the processing unit 1106 is configured to: whereinthe universal audio application control interface view includes anaffordance corresponding to adding the universal audio applicationcontrol interface view to the set of application views. Receive (e.g.,with receiving unit 1110) a user input for selecting the affordance, andin response to receiving the user input for selecting the affordance,add (e.g., with the adding unit 1112) the universal audio applicationcontrol interface view to the set of application views.

In some embodiments, the processing unit 1106 is configure to: at acompanion device with one or more processors and memory that is pairedwith the device display (e.g., with display unit 1102) the adaptive viewthat corresponds to a most recently opened application, wherein theadaptive view includes an affordance corresponding to adding theadaptive view to the preselected application views. Receive (e.g., withreceiving unit 1110) user input for selecting the affordance, and inresponse to receiving the user input for selecting the affordance, add(e.g., with adding unit 1112) the adaptive view that corresponds to themost recently opened application to the preselected application views.

In some embodiments, the processing unit 1106 is configured to: at acompanion device with one or more processors, touchscreen and memorythat is paired with the device display (e.g., with display unit 1102) aportion of the sequence of the set of application views. Receive (e.g.,with receiving unit 1110) an input at a location on the touchscreendisplaying an application view in a first position in the sequence ofthe set of application views. In response to the input, visuallydistinguish (e.g., with visually distinguishing unit 1128) the selectedapplication view with respect to the other application views in thesequence of the set of application views. Detect (e.g., with detectingunit 1124) movement, without breaking contact with touchscreen, of theinput on the application view to a second position in the sequence ofthe set of application views. In response to the detected movement ofthe input on the application view, move (e.g., with moving unit 1130)the selected application view to the second position in the sequence ofset of application views. Detect (e.g., with detecting unit 1124) abreak of the input with the touchscreen, and in response to the detectedbreak of the input with the touchscreen, reorder (e.g., with reorderingunit 1116) the application view to the second position in the sequenceof set of application views.

In some embodiments, the processing unit 1106 is configured to: at acompanion device to the device), wherein the companion device includesone or more processors and memory that is paired with the device,receive (e.g., with receiving unit 1110) an input on an application viewof the plurality of application views, the input, when receivedinitiates deletion of the application view from the set of applicationviews. In response to the input on the application view, delete (e.g.,with deleting unit 1119) the application view from the set ofapplication views.

The operations described above with reference to FIGS. 10A-10Q are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.11. For example, receiving operation 1002, and displaying operation 1004are, optionally, implemented by event sorter 170, event recognizer 180,and event handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190optionally utilizes or calls data updater 176 or object updater 177 toupdate the application internal state 192. In some embodiments, eventhandler 190 accesses a respective GUI updater 178 to update what isdisplayed by the application. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

FIGS. 12A-12G illustrates exemplary user interfaces for updating viewsin a set of application views, in accordance with some embodiments. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 13.

FIG. 12A illustrates device 600 with touch sensitive display 602. Userinterface 604 is displayed on touch-sensitive display 602. Userinterface 604, as illustrated in FIG. 12A, includes watch face 608 of awatch application.

Device 600 includes various input mechanisms that receives user input,such as, rotatable input mechanism 610, that is able to receive arotatable input (and may also receive a push input), and push inputmechanism 612 that is able to receive a push input.

Referring now to FIGS. 12A-12B, in response to receiving user input 1210at input mechanism 612, device 600 displays a plurality of applicationviews of a set of application views 630. The set of application viewsare a sequential list of application views that correspond to respectiveapplications. The set of application views 630 include preselectedapplication views. In some embodiments, the set of application viewsincludes an adaptive application view that corresponds to the mostrecently opened application that is not one of the application views.

In some embodiments, as shown in FIG. 12B, in response to user input1210, device 600 displays application views 633, 634, and 635.

As shown in FIG. 12B, application views 633, 634 and 635 are displayedin a respective first state. In some embodiments, application views 633,634 and 635 are the last viewed screen of the respective applications.For example, application view 634 is the last viewed screen of thestocks application.

Referring to FIG. 12C, in some embodiments, the set of application views630 are no longer displayed. For example, an application is opened(e.g., clock application), and in response to an opened application, theset of application views are no longer displayed.

Device 600, in some embodiments, automatically determines, without userinput, whether a predetermined criteria is met for updating at least oneapplication view of the set of application views to a second state. Inaccordance with the automatic determination, without user input, thatthe predetermined criteria is met, device 600 updates at least oneapplication view of the set of application views. In some embodiments,the predetermined criteria is a periodic timeout (e.g., every threeminutes). For example, at the end of each periodic timeout, one or moreof the application views is updated to an updated second state. In suchan example, application view 634 for the stock application is updatedwith current stock information.

In some embodiments, the predetermined criteria is change in dataassociated with the application view. For example, for a stocksapplication, the stock information may change frequently. As such, theapplication view corresponding to the stocks application, is updated inresponse to the change in stock information that is displayed in theapplication view. In some embodiments, each of the application views areupdated in the background when the predetermined criteria is met (e.g.,end of a periodic timeout, or change in information displayed in therespective application view).

In some embodiments, the updating of the application view in response tothe predetermined criteria being met can occur with the correspondingapplication being in one of various states, such as ready to be launched(e.g., become opened), an open or executing application, or a closedapplication. In particular, an open or executing application can be, butis not limited to an active application, which is currently displayed ona display screen of the device that the application is being used on, abackground application (or background processes), which is not currentlydisplayed, but one or more processes for the application are beingprocessed by one or more processors, and a suspended or hibernatedapplication, which is not running, but has state information that isstored in memory (volatile and non-volatile, respectively) and that canbe used to resume execution of the application.

In some embodiments, the automatic updating, without user input, for anapplication view occurs while the corresponding application is notcurrently displayed. In some embodiments, the automatic updating,without user input, for an application view occurs while thecorresponding application is launched. In some embodiments, theautomatic updating, without user input, for an application view occurswhile the corresponding application is unlaunched. In some embodiments,the automatic updating, without user input, for an application viewoccurs while the corresponding application is not active.

As described above, the applications associated with the set ofapplication views are stored in memory. As such, the updated applicationviews for the respective applications are also stored in memory.

Referring to FIGS. 12C-12D, a second user input 1212 is received, thesecond user input, when received, initiates display of the plurality ofapplication views of the set of application views 630. In response toreceiving the second user input 1212, device 600 displays the pluralityof application views of the set of application views 630 that includesthe at least one updated application view 634 updated to the secondstate. For example, device 600 displays application view 634 in anupdated second state that includes current stock information that isupdated from the first state, as depicted in FIG. 12B.

In some embodiments, referring to FIG. 12D, the displaying the pluralityof application views of the set of application views in a second statefurther includes displaying a first application view in an applicationview area (e.g., user interface 604), wherein the first application view(e.g., application 634) is an updated application view that is focused,and centered in the application view area.

Additionally, in some embodiments, at least a partial view of a secondapplication view (e.g., application views 633 and 635) are displayed inthe application view area, wherein the second application view issequential to the first application views, wherein the secondapplication view is not updated. For example, application views 633 and635 are not updated to a second state when application view 634 isupdated to a second state. As such, application views 633 and 635 arenot displayed in a second updated state when updated application view634 is displayed in a second application state.

In some embodiments, referring to FIG. 12E, the updated application viewof the stocks application is an adaptive application view and a set ofapplication view indicia is also displayed, wherein each of theapplication view indicia corresponds to a respective application view inthe set of application views. In particular, the application viewindicia 645 corresponding to the adaptive application view is visuallydistinguished with respect to the application view indicia correspondingto the preselected application views.

In some embodiments, while displaying the plurality of application viewsof the set of application views (e.g., application views 633, 634 and635 in FIG. 12D), a set of application view indicia 640 is displayed,wherein each of the application view indicia corresponds to a respectiveapplication view in the set of application views. An indiciacorresponding to a displayed application view is highlighted. A userinput, the user input, when received for scrolling to anotherapplication view in the set of application views (e.g., input 710 inFIG. 7A). In response to receiving the user input, the application viewsare scrolled to the another application view (e.g., FIG. 7B). Inaccordance to scrolling to the another application view, highlighting anapplication view indicia corresponding to the another application view,wherein the highlighting the application view corresponding to theanother application view includes: an initial highlighting brightness(e.g., FIG. 7K), and a final highlighting brightness, wherein thebrightness of the highlighting increases during the transition from theinitial highlighting brightness to the final highlighting brightness(e.g., FIG. 7L).

In some embodiments, it is determined whether a first timeout hasexpired since a most recent update of an application view. In responseto the first timeout expiring, displaying the application view in adimmed state. For example, referring to FIG. 12F, if the applicationview 634 is unable to be updated by the end of a first time period(e.g., five minutes), then the application view is dimmed (or visuallydistinguished) to indicate that the application view is unable to beupdated. In accordance with selection of the application view in thedimmed state, launching an application corresponding to the selectedapplication view. For example, in response to selecting application view634, while in the dimmed state, the stocks application is launched.

Furthermore, it is determined whether a second timeout (e.g., 30minutes) has expired since the most recent update of the applicationview, wherein a duration of the second timeout is longer than a durationof the first timeout. In response to the second timeout expiring,displaying an application view that does not include a screen shot of acorresponding application. For example, referring to FIG. 12G, if theapplication view 634 is unable to be updated by the end of a second timeperiod (e.g., 30 minutes), then the displayed application view does notinclude a screen shot of the stocks application. In accordance withselection of the application view that does not include a screen shot ofthe corresponding application, the corresponding application islaunched. For example, in response to selecting application view 634that does not include a screen shot of the stocks application, thestocks application is launched.

FIG. 13 is a flow diagram illustrating a method for updating applicationviews in a set of application views using an electronic device inaccordance with some embodiments. Method 1300 is performed at a device(e.g., 100, 300, 500, 600, or 900) with a display, one or processors andmemory. Some operations in method 1300 are, optionally, combined, theorder of some operations is, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 1300 provides an intuitive way for updatingapplication views in a set of application views. The method reduces thecognitive burden on a user for selecting an application via updatedapplication views in a set of application views, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user select an application via updated applicationviews in a set of application views faster and more efficientlyconserves power and increases the time between battery charges.

At block 1302, a first user input (e.g., user input 1210) is received,the first user input when received, initiates display of a plurality ofapplication views of a set of application views 630, wherein the set ofapplication views includes preselected application views, the pluralityof application views of the set of application views displayed in arespective first state (e.g., FIG. 12A).

At block 1304, it is automatically determined, without user input,whether a predetermined criteria is met for updating at least oneapplication view of the set of application views to a second state. Insome embodiments, the predetermined criteria is an end of apredetermined timeout. In some embodiments, the predetermine criteria isthe change of data that is displayed on the application view.

At block 1306, in accordance with the automatic determination, withoutuser input, that the predetermined criteria is met, the at least oneapplication view (e.g., application view 634 in FIG. 12D) of the set ofapplication views to the second state is updated

At block 1308, a second user input (e.g., input 1212) is received, thesecond user input, when received, display of the plurality ofapplication views of the set of application views is initiated.

At block 1310, in response to receiving the second user input (e.g.,input 1212), the plurality of application views of the set ofapplication views that includes the at least one updated applicationview is updated to the second state (e.g., FIG. 12D).

In some embodiments, the set of application views further includes anadaptive view that corresponds to a most recently opened applicationthat is not one of the preselected application views.

In some embodiments, the automatic updating, without user input, for anapplication view occurs while the corresponding application is notcurrently displayed. In some embodiments, the automatic updating,without user input, for an application view occurs while thecorresponding application is launched. In some embodiments, theautomatic updating, without user input, for an application view occurswhile the corresponding application is unlaunched. In some embodiments,the automatic updating, without user input, for an application viewoccurs while the corresponding application is not active.

In some embodiments, wherein displaying the plurality of applicationviews of the set of application views in a second state comprisesdisplaying a first application view in an application view area (e.g.,user interface 604), wherein the first application view is an updatedapplication view that is focused, and centered in the application viewarea (e.g., application view 634 in FIG. 12D), and displaying at least apartial view of a second application view in the application view area,wherein the second application view is sequential to the firstapplication views, wherein the second application view is not updated(e.g., application views 633 and 635 in FIG. 12D).

In some embodiments, in response to determining that the predeterminedcriteria is met, updating each of the application views in the set ofapplication views. For example, each of the application views areupdated at the end of a timeout.

In some embodiments, is s determined whether a first timeout has expiredsince a most recent update of an application view. In response to thefirst timeout expiring, displaying the application view in a dimmedstate (e.g., FIG. 12F). In accordance with selection of the applicationview in the dimmed state, launching an application corresponding to theselected application view (e.g., stocks application is launched inresponse to selection of application view 634). Determining whether asecond timeout has expired since the most recent update of theapplication view, wherein a duration of the second timeout is longerthan a duration of the first timeout. In response to the second timeoutexpiring, displaying an application view that does not include a screenshot of a corresponding application (e.g., FIG. 12G), and in accordancewith selection of the application view that does not include a screenshot of the corresponding application, launching the correspondingapplication (e.g., stocks application is launched in response toselection of application view 634).

In some embodiments, while displaying the plurality of application viewsof the set of application views, displaying a set of application viewindicia (e.g., FIG. 12B), wherein each of the application view indiciacorresponds to a respective application view in the set of applicationviews, wherein the application view indicia corresponding to theadaptive view is visually distinguished with respect to the applicationview indicia corresponding to the preselected application views (e.g.FIG. 12E).

In some embodiments, while displaying the plurality of application viewsof the set of application views, displaying a set of application viewindicia, wherein each of the application view indicia corresponds to arespective application view in the set of application views (e.g., FIG.12B), and highlighting an indicia corresponding to a displayedapplication view. Receiving a user input, the user input, when receivedfor scrolling to another application view in the set of applicationviews (e.g., FIG. 7A). In response to receiving the user input,scrolling to the another application view (e.g., FIG. 7B). In accordanceto scrolling to the another application view, highlighting anapplication view indicia corresponding to the another application view(e.g., FIG. 7B, wherein the highlighting the application viewcorresponding to the another application view includes an initialhighlighting brightness (e.g., FIG. 7K), and a final highlightingbrightness, wherein the brightness of the highlighting increases duringthe transition from the initial highlighting brightness to the finalhighlighting brightness (e.g., FIG. 7L).

Note that details of the processes described above with respect tomethod 1300 (e.g., FIG. 13) are also applicable in an analogous mannerto the methods described above. For example, method 1300 optionallyincludes one or more of the characteristics of the various methodsdescribed above with reference to method 1000. For example, the viewingof application views, in accordance to method 1100 may include the viewof updated application views, in accordance to method 100. For brevity,these details are not repeated below.

In accordance with some embodiments, FIG. 14 shows an exemplaryfunctional block diagram of an electronic device 1400 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 1400 are configured to perform the techniques described above.The functional blocks of the device 1400 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 14 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 14, an electronic device 1400 includes a display unit1402 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 1404 configured to receive contacts, and aprocessing unit 1406 coupled to the display unit 1402 and, optionally,the touch-sensitive surface unit 1104. In some embodiments, theprocessing unit 1406 includes a receiving unit 1410, a determining unit1412, an updating unit 1414, a launching unit 1416, a highlighting unit1418, and a scrolling 1420.

The processing unit 1406 is configured to: receive (e.g., with thereceiving unit 1410) a first user input, the first user input whenreceived, initiating display of a plurality of application views of aset of application views, wherein the set of application views includespreselected application views, the plurality of application views of theset of application views displayed in a respective first state (e.g.,FIG. 12B). Automatically determine (e.g., determining unit 1412) with,without user input, whether a predetermined criteria is met for updatingat least one application view of the set of application views to asecond state. In accordance with the automatic determination, withoutuser input, that the predetermined criteria is met, update (e.g., withupdating unit 1414) the at least one application view of the set ofapplication views to the second state. Receive (e.g., with receivingunit 1410) a second user input, the second user input, when received,initiating display of the plurality of application views of the set ofapplication views (e.g., FIG. 12D). In response to receiving the seconduser input, display (e.g., with display unit 1402) the plurality ofapplication views of the set of application views that includes the atleast one updated application view updated to the second state (e.g.,FIG. 12D).

The processing unit 1406 is configured to: display (e.g., with thedisplay unit 1402) the plurality of application views of the set ofapplication views in a second state that comprises display a firstapplication view in an application view area, wherein the firstapplication view is an updated application view that is focused, andcentered in the application view area (e.g., FIG. 12D), and display(e.g., with displaying unit 1402) at least a partial view of a secondapplication view in the application view area, wherein the secondapplication view is sequential to the first application views, whereinthe second application view is not updated (e.g., FIG. 12D).

The processing unit 1406 is configured to: in response to determiningthat the predetermined criteria is met, update (e.g., with updating unit1414) each of the application views in the set of application views.

The processing unit 1406 is configured to: determine (e.g., withdetermining unit 1412) whether a first timeout has expired since a mostrecent update of an application view. In response to the first timeoutexpiring, display (e.g., with displaying unit 1402) the application viewin a dimmed state (e.g., FIG. 12F). In accordance with selection of theapplication view in the dimmed state, launch (e.g., with launching unit1416) an application corresponding to the selected application view.Determine (e.g., with determining unit 1412) whether a second timeouthas expired since the most recent update of the application view,wherein a duration of the second timeout is longer than a duration ofthe first timeout. In response to the second timeout expiring, display(e.g., with displaying unit 1402) an application view that does notinclude a screen shot of a corresponding application (e.g., FIG. 12G),and in accordance with selection of the application view that does notinclude a screen shot of the corresponding application, launch (e.g.,with launching unit 1416) the corresponding application.

The processing unit 1406 is configured to: while displaying theplurality of application views of the set of application views, display(e.g., with display unit 1402) a set of application view indicia (e.g.,FIG. 12B), wherein each of the application view indicia corresponds to arespective application view in the set of application views, wherein theapplication view indicia corresponding to the adaptive view is visuallydistinguished with respect to the application view indicia correspondingto the preselected application views (e.g. FIG. 12E).

The processing unit 1406 is configured to: while displaying theplurality of application views of the set of application views, display(e.g., with display unit 1402) a set of application view indicia,wherein each of the application view indicia corresponds to a respectiveapplication view in the set of application views (e.g., FIG. 12B), andhighlight (e.g., with highlighting unit 1418) an indicia correspondingto a displayed application view. Receive (e.g., with receiving unit1410) a user input, the user input, when received for scrolling toanother application view in the set of application views (e.g., FIG.7A). In response to receiving the user input, scroll (e.g., withscrolling unit 1420) to the another application view (e.g., FIG. 7B). Inaccordance to scrolling to the another application view, highlight(e.g., with highlighting unit 1418) an application view indiciacorresponding to the another application view (e.g., FIG. 7B), whereinthe highlighting the application view corresponding to the anotherapplication view includes an initial highlighting brightness (e.g., FIG.7K), and a final highlighting brightness, wherein the brightness of thehighlighting increases during the transition from the initialhighlighting brightness to the final highlighting brightness (e.g., FIG.7L).

In some embodiments, the set of application views further includes anadaptive view that corresponds to a most recently opened applicationthat is not one of the preselected application views (e.g., FIG. 12E).

In some embodiments, the automatic updating, without user input, for anapplication view occurs while the corresponding application is notcurrently displayed. In some embodiments, the automatic updating,without user input, for an application view occurs while thecorresponding application is launched. In some embodiments, theautomatic updating, without user input, for an application view occurswhile the corresponding application is unlaunched. In some embodiments,the automatic updating, without user input, for an application viewoccurs while the corresponding application is not active.

The operations described above with reference to FIG. 13 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.14. For example, receiving operation 1302, determining operation 1304,determining operation 1306, receiving operation 1308 and displayingoperation 1310 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

FIGS. 15A-15C illustrates exemplary user interfaces for displaying viewsin a set of application views, in accordance with some embodiments. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 16.

FIG. 15A illustrates device 600 with touch sensitive display 602. Userinterface 604 is displayed on touch-sensitive display 602. Userinterface 604, as illustrated in FIG. 15A, includes watch face 608 of awatch application.

Device 600 includes various input mechanisms that receives user input,such as, rotatable input mechanism 610, that is able to receive arotatable input (and may also receive a push input), and push inputmechanism 612 that is able to receive a push input.

Referring now to FIGS. 15A-15C, device 600 displays a watch face (FIG.15A). A first user input 1510 is received, the first user input, whenreceived initiating display of a plurality of application views (e.g.,application views 633, 634 and 635) of a set of application views 630,wherein the set of application views includes preselected applicationviews.

Referring to FIG. 15B, in response to receiving the first user input,device 600 displays the plurality of application views of the set ofapplication views in a first state. For example, application view 634that corresponds to a weather application is center focused anddisplayed. Additionally, at least a portion of application views 633 and635 are displayed adjacent to application view 634.

Still referring to FIG. 15B, a second user input (e.g., input 1512) onapplication view 634 of the plurality of displayed application views isreceived, the second user input, when received initiating launch of anapplication corresponding with the application view selected by thesecond user input.

Referring to FIG. 15C, in response to receiving the second user input,the plurality of displayed application views is replaced by displaying auser interface of the launched application. For example, device 600displays the weather application and replaces the display of applicationviews 633, 634, and 635.

In some embodiments, referring to FIG. 15B, swipe gesture 1514 (e.g.,right swipe gesture) is received for scrolling through the set ofapplication views 630. In response to receiving the swipe gesture 1514,device scrolls through the set of application views and replaces theinitially displayed plurality of application views 633, 634, and 635with a second set of application views, such as application view 631 and632 (e.g., FIG. 6B).

In some embodiments, the displayed watch face (e.g., FIG. 15A) isreplaced by the displaying the plurality of application views of the setof application views in a second state (e.g., FIG. 15B).

FIG. 16 is a flow diagram illustrating a method for viewing applicationviews in a set of application views using an electronic device inaccordance with some embodiments. Method 1600 is performed at a device(e.g., 100, 300, 500, 600, or 900) with a display, one or processors andmemory. Some operations in method 1600 are, optionally, combined, theorder of some operations is optionally, changed, and some operationsare, optionally, omitted.

As described below, method 1600 provides an intuitive way for viewingapplication views in a set of application views. The method reduces thecognitive burden on a user for viewing application views in a set ofapplication views, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user toview application views in a set of application views faster and moreefficiently conserves power and increases the time between batterycharges.

At block 1602, a watch face is displayed (e.g., FIG. 15A)

At block 1604, a first user input is received (e.g., user input 1510),the first user input, when received initiating display of a plurality ofapplication views of a set of application views, wherein the set ofapplication views includes preselected application views.

At block 1606, in response to receiving the first user input, theplurality of application views of the set of application views aredisplayed (e.g., FIG. 15B)

At block 1608, a second user input (e.g., user input 1512) on anapplication view of the plurality of displayed application views isreceived, the second user input, when received initiating launch of anapplication corresponding with the application view selected by thesecond user input (e.g., FIG. 15B)

At block 1610, in response to receiving the second user input, theplurality of displayed application views are replaced by displaying auser interface of the launched application (e.g., FIG. 15C).

In some embodiments, referring to FIG. 15B, swipe gesture 1514 (e.g.,right swipe gesture) is received for scrolling through the set ofapplication views 630. In response to receiving the swipe gesture 1514,set of application views are scrolled and the initially displayedplurality of application views 633, 634, and 635 are replaced with asecond set of application views, such as application view 631 and 632(e.g., FIG. 6B).

In some embodiments, the displayed watch face (e.g., FIG. 15A) isreplaced by the displaying the plurality of application views of the setof application views in a second state (e.g., FIG. 15B).

Note that details of the processes described above with respect tomethod 1600 (e.g., FIG. 16) are also applicable in an analogous mannerto the methods described above. For example, method 1600 optionallyincludes one or more of the characteristics of the various methodsdescribed above with reference to methods 1000 and 1300. For example,the viewing of application views, in accordance to method 1600 mayinclude the embodiments of viewing of updated application views, inaccordance to method 1000, and embodiments of updating of applicationviews, in accordance with method 1300. For brevity, these details arenot repeated below.

In accordance with some embodiments, FIG. 17 shows an exemplaryfunctional block diagram of an electronic device 1700 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 1700 are configured to perform the techniques described above.The functional blocks of the device 1700 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 17 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 17, an electronic device 1700 includes a display unit1702 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 7404 configured to receive contacts, and aprocessing unit 1706 coupled to the display unit 1702 and, optionally,the touch-sensitive surface unit 1704. In some embodiments, theprocessing unit 1706 includes a receiving unit 1710, a replacing unit1712, and a scrolling 1720.

The processing unit 1706 is configured to: display (e.g., with displayunit 1702) a watch face (e.g., FIG. 15A). Receive (e.g., with receivingunit 1710) a first user input, the first user input, when receivedinitiating display of a plurality of application views of a set ofapplication views, wherein the set of application views includespreselected application views (e.g., FIG. 15B).

In response to receiving the first user input, display (e.g., withdisplay unit 1702) the plurality of application views of the set ofapplication views (e.g., FIG. 15B). Receive (e.g., with receiving unit1710) a second user input on an application view of the plurality ofdisplayed application views (e.g., FIG. 15B), the second user input,when received initiating launch of an application corresponding with theapplication view selected by the second user input. In response toreceiving the second user input, replace (e.g., with replacing unit1712) the plurality of displayed application views by displaying a userinterface of the launched application (e.g., FIG. 15C).

The processing unit 1706 is configured to: receive (e.g., with receivingunit 1710) a swipe gesture for scrolling through the set of applicationviews (e.g., FIG. 15B). In response to receiving the swipe gesture,scroll (e.g., with scrolling unit 1714) through the set of applicationviews and replace (e.g., with replacing unit 1712) the initiallydisplayed plurality of application views with a second set ofapplication views (e.g., FIG. 6B).

The processing unit 1706 is configured to: replace (e.g., with replacingunit 1712) the displayed watch face by the displaying the plurality ofapplication views of the set of application views (e.g., FIG. 15B).

The operations described above with reference to FIG. 16 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.17. For example, displaying operation 1602, receiving operation 1604,displaying operation 1606, receiving operation 1608 and replacingoperation 1610 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content that maybe of interest to them. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, home addresses,or any other identifying information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables calculatedcontrol of the delivered content. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data will comply withwell-established privacy policies and/or privacy practices. Inparticular, such entities should implement and consistently use privacypolicies and practices that are generally recognized as meeting orexceeding industry or governmental requirements for maintaining personalinformation data private and secure. For example, personal informationfrom users should be collected for legitimate and reasonable uses of theentity and not shared or sold outside of those legitimate uses. Further,such collection should occur only after receiving the informed consentof the users. Additionally, such entities would take any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for targeted content delivery services. Inyet another example, users can select to not provide precise locationinformation, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publically available information.

What is claimed is:
 1. An electronic device, comprising: a display; oneor more processors; one or more input devices; a memory; and one or moreprograms, wherein the one or more programs are stored in memory andconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving a user input, the input,when received initiating display of a plurality of application views ofa set of application views; and in response to receiving the user input,displaying the plurality of application views of the set of applicationviews, wherein the set of application views includes preselectedapplication views and an adaptive view that corresponds to a mostrecently opened application that is not one of the preselectedapplication views.
 2. The electronic device of claim 1, the one or moreprograms further including instructions for: displaying the adaptiveview that corresponds to a most recently opened application, wherein theadaptive view includes an affordance corresponding to adding theadaptive view to the preselected application views; receiving a userinput corresponding to selection of the affordance; and in response toreceiving the user input for selecting the affordance, adding theadaptive view that corresponds to the most recently opened applicationto the preselected application views.
 3. The electronic device of claim1, wherein the set of application views are displayed in a sequence, theone or more programs further including instructions for: displaying theadaptive view at a terminus of the sequence of the set of applicationviews.
 4. The electronic device of claim 1, wherein the user input isreceived while displaying an open application that is the most recentlyopened application that is not one of the preselected application views,the one or more programs further including instructions for: further inresponse to receiving the user input, displaying the adaptive view thatcorresponds to the most recently opened application that is not one ofthe preselected application views, wherein the adaptive view includes anaffordance corresponding to adding the adaptive view to the preselectedapplication views, receiving a user input corresponding to selection ofthe affordance; and in response to receiving the user input forselecting the affordance, adding the adaptive view that corresponds tothe most recently opened application to the preselected applicationviews.
 5. The electronic device of claim 1, the one or more programsfurther including instructions for: detecting launch of an application,wherein the adaptive view and the preselected application views of theset of application views do not correspond with the launchedapplication; and in response to detecting the launch of the application,updating the adaptive view to correspond with the launched application.6. The electronic device of claim 1, wherein the set of applicationviews are displayed in a sequence, the one or more programs furtherincluding instructions for: in response to receiving user inputcorresponding to display of the sequence of the set of applicationviews, displaying a subset of application views of the sequence of theset of application views, wherein the displaying the subset ofapplication views comprises: displaying an application view of a mostrecently opened application in a center of the sequence of the subset ofapplication views.
 7. The electronic device of claim 1, wherein the setof application views are displayed in a sequence, the one or moreprograms further including instructions for: in response to receivinguser input corresponding to display of the sequence of the set ofapplication views, displaying a subset of application views of thesequence of the set of application views, wherein the displaying thesubset of application views comprises: displaying a first applicationview in the sequence of the set of application in a center of thesequence of the subset of application views; and displaying at least apartial view of a second application view sequential to the firstapplication view in the sequence of the set of application views,wherein the second application view is dimmed with respect to the firstapplication view.
 8. The electronic device of claim 1, the one or moreprograms further including instructions for: while the applicationassociated with the adaptive view is not opened, displaying the adaptiveview; receiving a user input corresponding to the adaptive view; and inresponse to receiving the user input corresponding to the adaptive view,launching the associated application.
 9. The electronic device of claim1, the one or more programs further including instructions for:displaying a portion of the sequence of the set of application views;receiving an input on an application view in a first position in thesequence of the set of application views; in response to the input onthe application view, visually distinguishing the selected applicationview with respect to the other application views in the sequence of theset of application views; detecting movement of the input on theapplication view to a second position in the sequence of the set ofapplication views; in response to the detected movement of the input onthe application view, moving the selected application view to the secondposition in the sequence of set of application views; detecting a breakof the input on the application view; and in response to the detectedbreak of the input on the application view, reordering the applicationview to the second position in the sequence of set of application views.10. The electronic device of claim 1, the one or more programs furtherincluding instructions for: receiving an input on an application view ofthe plurality of application views, the input, when received initiatingdeleting the application view from the set of application views; and inresponse to the input on the application view, deleting the applicationview from the set of application views.
 11. The electronic device ofclaim 1, the one or more programs further including instructions for:receiving a swipe gesture for scrolling through the set of applicationviews; and in response to receiving the swipe gesture: in accordancewith the velocity of the swipe gesture below a predetermined velocitythreshold, scrolling to an adjacent application view; and in accordanceto the velocity of the swipe gesture above the predetermined velocitythreshold, scrolling through a plurality of application views of the setof application views.
 12. The electronic device of claim 1, the one ormore programs further including instructions for: receiving a userinput, the user input, when received initiating scrolling to an adjacentapplication view in set of application views; and in response toreceiving the user input, scrolling to the adjacent application view inthe set of application views, wherein the scrolling to the adjacentapplication view includes a decrease in velocity based on apredetermined coefficient of friction.
 13. The electronic device ofclaim 1, the one or more programs further including instructions for:while displaying the plurality of application views in a display area,receiving an input at a bottom edge of the display area, the input, whenreceived initiating scrolling of the application views; in response tothe input at an edge of the display area, moving the application viewsaway from the bottom edge of the display area; detecting movement of theinput along the bottom edge of the display area; and in response to thedetected movement of the input along the bottom edge of the displayarea, scrolling through the set of application views.
 14. The electronicdevice of claim 1, the one or more programs further includinginstructions for: while displaying the plurality of application views ofthe set of application views, displaying a set of application viewindicia, wherein each of the application view indicia corresponds to arespective application view in the set of application views, wherein theapplication view indicia corresponding to the adaptive view is visuallydistinguished with respect to the application view indicia correspondingto the preselected application views.
 15. The electronic device of claim1, the one or more programs further including instructions for: whiledisplaying the plurality of application views of the set of applicationviews, displaying a set of application view indicia, wherein each of theapplication view indicia corresponds to a respective application view inthe set of application views; highlighting an indicia corresponding to adisplayed application view; receiving a user input, the user input, whenreceived for scrolling to another application view in the set ofapplication views; in response to receiving the user input, scrolling tothe another application view; in accordance to scrolling to the anotherapplication view, highlighting an application view indicia correspondingto the another application view, wherein the highlighting theapplication view corresponding to the another application view includes:an initial highlighting brightness; and a final highlighting brightness,wherein the brightness of the highlighting increases during thetransition from the initial highlighting brightness to the finalhighlighting brightness.
 16. The electronic device of claim 1, the oneor more programs further including instructions for: while an audioapplication is playing audio content, wherein the audio applicationincludes an application-specific control interface, wherein the set ofapplication views does not include an application view corresponding tothe audio application: updating the set of application views with auniversal audio application control interface view corresponding to auniversal audio application control interface, wherein the universalaudio application control interface is different than theapplication-specific control interface; receiving a user input on theuniversal audio application control interface view, the user input, whenreceived initiating launching the universal audio application controlinterface; and in response to receiving the user input, displaying theuniversal audio application control interface for controlling theplayback of the audio content playing on the audio application.
 17. Theelectronic device of claim 16, wherein the universal audio applicationcontrol interface view includes an affordance corresponding to addingthe universal audio application control interface view to the set ofapplication views, the one or more programs further includinginstructions for: receiving a user input for selecting the affordance;and in response to receiving the user input for selecting theaffordance, adding the universal audio application control interfaceview to the set of application views.
 18. The electronic device of claim1, the one or more programs further including instructions for: at acompanion device with one or more processors and memory that is pairedwith the device: displaying the adaptive view that corresponds to a mostrecently opened application, wherein the adaptive view includes anaffordance corresponding to adding the adaptive view to the preselectedapplication views; receiving a user input for selecting the affordance;and in response to receiving the user input for selecting theaffordance, adding the adaptive view that corresponds to the mostrecently opened application to the preselected application views. 19.The electronic device of claim 1, the one or more programs furtherincluding instructions for: at a companion device with one or moreprocessors, touchscreen and memory that is paired with the device:displaying a portion of the sequence of the set of application views;receiving an input at a location on the touchscreen displaying anapplication view; in response to the input, visually distinguishing theselected application view with respect to the other application views inthe sequence of the set of application views; detecting movement,without breaking contact with touchscreen, of the input on theapplication view; in response to the detected movement of the input onthe application view, moving the selected application view to the secondposition in the sequence of set of application views; detecting a breakof the input with the touchscreen; and in response to the detected breakof the input with the touchscreen, reordering the application view tothe second position in the sequence of set of application views.
 20. Theelectronic device of claim 1, the one or more programs further includinginstructions for: at a companion device to the device, wherein thecompanion device includes one or more processors and memory that ispaired with the device: receiving an input on an application view of theplurality of application views, the input, when received initiatingdeletion of the application view from the set of application views; andin response to the input on the application view, deleting theapplication view from the set of application views.
 21. A method,comprising: at a device with one or more processors and memory:receiving a user input, the input, when received initiating display of aplurality of application views of a set of application views; and inresponse to receiving the user input, displaying the plurality ofapplication views of the set of application views, wherein the set ofapplication views includes preselected application views and an adaptiveview that corresponds to a most recently opened application that is notone of the preselected application views.
 22. A non-transitorycomputer-readable storage medium storing one or more programs configuredto be executed by one or more processors of an electronic device with adisplay and one or more input devices, the one or more programsincluding instructions for: receiving a user input, the input, whenreceived initiating display of a plurality of application views of a setof application views; and in response to receiving the user input,displaying the plurality of application views of the set of applicationviews, wherein the set of application views includes preselectedapplication views and an adaptive view that corresponds to a mostrecently opened application that is not one of the preselectedapplication views.